Cloud-based proximity pairing and switching for peer-to-peer devices

ABSTRACT

A first wireless communication device (UE device) associated with a certain user (or included in a specified set/group of UE devices) may establish a first communication link with an accessory device according to a short-range radio access technology, and transmit link (pairing) information associated with the first communication link to a server, such as a cloud-based server. The server may share this (first) link information with other UE devices associated with the same user (or belonging to the same specified group of UE devices as the first UE device). Link information associated with the other UE devices (i.e. second link information) may equally be shared with the accessory device, and the other UE devices and accessory device may use the first link information and second link information in establishing respective communication links between any of the other UE devices and the accessory device without having to undergo a pairing procedure.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.15/911,644 titled “Cloud Based Proximity Pairing and Switching forPeer-to-Peer Devices” and filed on Mar. 5, 2018, now U.S. Pat. No.10,419,912, which itself is a continuation of U.S. patent applicationSer. No. 14/871,487 titled “Cloud Based Proximity Pairing and Switchingfor Peer-to-Peer Devices” and filed on Sep. 30, 2015, now U.S. Pat. No.9,913,079, which claims benefit of priority of U.S. Provisional PatentApplication Ser. No. 62/171,844 titled “Cloud-Based Proximity Pairingand Switching for Peer-to-Peer Devices”, filed on Jun. 5, 2015, all ofwhich are hereby incorporated by reference in their entirety as thoughfully and completely set forth herein.

The claims in the instant application are different than those of theparent application or other related applications. The Applicanttherefore rescinds any disclaimer of claim scope made in the parentapplication or any predecessor application in relation to the instantapplication. The Examiner is therefore advised that any such previousdisclaimer and the cited references that it was made to avoid, may needto be revisited. Further, any disclaimer made in the instant applicationshould not be read into or against the parent application or otherrelated applications.

FIELD OF THE INVENTION

The present application relates to electronic devices, includingestablishment of and switching between pairing sessions between anaccessory device and two or more electronic devices.

DESCRIPTION OF THE RELATED ART

In recent years electronic devices have become increasinglysophisticated. Electronic devices, including smart phones, smartwatches, smart glasses, tablet computers, and notebook computers, areoften able to communicate with numerous types of supportive or accessorydevices such as keyboards, mice, trackpads, headsets, speakers, remotecontrollers, videogame controllers, etc. Such accessory devices maysupport one or more of various communications technologies, includingwired and wireless technologies, in order to connect, or pair, withelectronic devices. In particular, these devices often utilize shortrange wireless communication technologies and standards, such as IEEE802.11 (WLAN or Wi-Fi), or BLUETOOTH™ (BT) or BLUETOOTH™ Low Energy(BTLE), among others.

Short range wireless communication technologies are oftentimes used toestablish wireless personal area networks (WPANs). WPANs can be used forcommunication among the electronic devices themselves (intrapersonalcommunication), or for connecting to a higher level network and theInternet (an uplink), or for connecting accessory devices with theelectronic devices (pairing). Other short range wireless communicationtechnologies used in establishing WPANs include Wireless USB™, INSTEON™,IrDA™, and the like. The reach of a WPAN can vary from a few centimetersto a few meters. One primary concept of WPANs is referred to as“plugging in”. For example, when any two WPAN-equipped devices come intoclose proximity (within several meters of each other), they canestablish communications with each other as if they were connected by acable. Another feature associated with WPAN-enabled devices and/oraccessories is the ability of each device/accessory to selectively lockout other devices/accessories, preventing needless interference orunauthorized access to information.

As mentioned above, electronic devices are often capable of pairing withone or more accessory devices, enabling direct peer-to-peercommunications between the paired devices. Pairing an accessory deviceand an electronic device often requires a prescribed procedure and/oractions in order to establish a functioning connection. Therefore,further improvements in the field are desired.

SUMMARY OF THE INVENTION

Embodiments are presented herein of, inter alia, improved systems andmethods for sharing an accessory device among multiple electronicdevices such that the electronic devices may efficiently transition toand from being paired with the accessory device.

In some scenarios, a user may desire to utilize an accessory deviceacross multiple other electronic devices as necessary. For example, auser may wish to use a BLUETOOTH™ (BT) headset with a mobile phone, e.g.an iPhone™, during one period of time, then use the same headset with atablet computer (e.g. an iPad™) at another time, and possibly with awearable electronic device (e.g. an Apple Watch™) at yet another time.However, transitioning an accessory device from being paired with (andthus useable by) a first electronic device to being paired with a secondelectronic device and a third electronic device (etc.) may presentinefficiencies.

In some embodiments, a first user equipment (UE) device associated witha certain user (or included in a specified set/group of UE devices) mayestablish a first communication link with an accessory device andtransmit link (pairing) information associated with this communicationlink to a server, such as a cloud server. The server may share this(first) link information with other UEs associated with the same user asthe first UE (or belonging to the same specified group of UE devices asthe first UE device). Link information associated with these other UEdevices (i.e. second link information) may equally be shared with theaccessory device, and the first link information and second linkinformation may then be useable by the other UE devices and theaccessory device in establishing respective communication links betweenany of the other UE devices and the accessory device.

Some embodiments may be implemented in a device that comprises at leastone antenna, one or more radios implementing one or more wireless radioaccess technologies (e.g., Wi-Fi or Bluetooth), and a processing elementcoupled to the at least one antenna. The device may communicate with oneor more other accessory devices. Note that the techniques describedherein may be implemented in and/or used with a number of differenttypes of devices, including but not limited to, computer systems, accesspoints, cellular phones, portable media players, tablet computers,wearable devices, and various other computing devices.

Proximity can be used to prompt pairing of devices through a short rangewireless communication protocol, e.g. BLUETOOTH™ (BT) low-energy (BTLE).When several hosts are in the vicinity, the user interface (UI) forproximity pairing may appear only on the host with which the accessoryis attempting to pair. Cloud-based proximity pairing/switching helpslimit the pairing options for an accessory to a specified or selectgroup of devices, e.g. to a user's iCloud™ registered devices. When anaccessory device is paired to one of a set of devices, the accessory,e.g., the BT stack, may send the link information associated with thepairing and the first device to other devices in the set. The link keysand/or other connection information associated with the other devices inthe set also may be shared by the currently connected device with theaccessory device. That is, link keys and/or other connection informationassociated with the other devices in the set may also be provided by thecurrently connected device to the accessory device. When the accessorydevice is within a particular proximity of another user device from theset of user devices, a disconnect message may be sent, e.g., over thecloud, to the currently connected device, enabling proximity-basedswitching of the accessory device to another device of the set ofdevices.

Further to the above, easy pairing between accessory devices and userdevices may be performed according to a variety of different scenarios.In a first example, user devices and accessories (or accessory devices)may be connected over a secure transport such as Universal Serial Bus(USB) or secure Wi-Fi and the existing transport may be used forexchanging link information, e.g. security credentials. In a secondexample, when a short range wireless communications connection, e.g., aBLUETOOTH™ connection, is desired between more than two devices, thedevice that has a connection with the other two devices may act as arelay to transfer link information, such as BLUETOOTH™ securitycredentials, over the existing BLUETOOTH™ connections to establish athird connection without having to go through a pairing procedure.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example wireless communication system in which a firstdevice connects over BLUETOOTH™ and Wi-Fi to various other devices,according to some embodiments;

FIG. 2 shows an example wireless communication system in which a firstcomputer system connects over BLUETOOTH™ and Wi-Fi to various otherdevices, according to some embodiments;

FIG. 3 is a block diagram illustrating an example user device accordingto some embodiments;

FIG. 4 is a flowchart illustrating an example method by which anaccessory device switches from being paired with a first device to beingpaired with a second device, according to some embodiments;

FIG. 5 shows an example communication system in which an accessorydevice is wirelessly connected to a first user device according to someembodiments;

FIG. 6 shows the communication system from FIG. 5, in which theaccessory device is disconnected from the first user device and becomewirelessly connected to a second user device according to someembodiments; and

FIG. 7 shows an example communication system in which various devicesare interconnected through wired and wireless connections, according tosome embodiments.

While features described herein are susceptible to various modificationsand alternative forms, specific embodiments thereof are shown by way ofexample in the drawings and are herein described in detail. It should beunderstood, however, that the drawings and detailed description theretoare not intended to be limiting to the particular form disclosed, but onthe contrary, the intention is to cover all modifications, equivalentsand alternatives falling within the spirit and scope of the subjectmatter as defined by the appended claims.

DETAILED DESCRIPTION OF THE EMBODIMENTS Acronyms

Various acronyms are used throughout the present application.Definitions of the most prominently used acronyms that may appearthroughout the present application are provided below:

UE: User Equipment

RF: Radio Frequency

AP: Access Point

BT: Bluetooth

BTLE: Bluetooth Low Energy

BTLEA: Bluetooth Low Energy for Audio

TDD: Time Division Duplexing

TX: Transmission/Transmit

RX: Reception/Receive

LAN: Local Area Network

WLAN: Wireless LAN, also referred to as Wi-Fi

RAT: Radio Access Technology

RSSI: Received Signal Strength Indicator

Wi-Fi: Wireless Local Area Network (WLAN) RAT based on the Institute ofElectrical and Electronics Engineers' (IEEE) 802.11 standards

Terms

The following is a glossary of terms that may appear in the presentapplication:

Memory Medium—Any of various types of memory devices or storage devices.The term “memory medium” is intended to include an installation medium,e.g., a CD-ROM, floppy disks 104, or tape device; a computer systemmemory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM,Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media,e.g., a hard drive, or optical storage; registers, or other similartypes of memory elements, etc. The memory medium may comprise othertypes of memory as well or combinations thereof. In addition, the memorymedium may be located in a first computer system in which the programsare executed, or may be located in a second different computer systemwhich connects to the first computer system over a network, such as theInternet. In the latter instance, the second computer system may provideprogram instructions to the first computer system for execution. Theterm “memory medium” may include two or more memory mediums which mayreside in different locations, e.g., in different computer systems thatare connected over a network. The memory medium may store programinstructions (e.g., embodied as computer programs) that may be executedby one or more processors and/or processing elements.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Computer System (or Computer)—any of various types of computing orprocessing systems, including a personal computer system (PC), mainframecomputer system, workstation, network appliance, Internet appliance,personal digital assistant (PDA), television system, grid computingsystem, or other device or combinations of devices. In general, the term“computer system” may be broadly defined to encompass any device (orcombination of devices) having at least one processor that executesinstructions from a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications. Also referred to as wireless communication devices.Examples of UE devices include mobile telephones or smart phones (e.g.,iPhone™, Android™-based phones) and tablet computers such as iPad™,Samsung Galaxy™, etc., portable gaming devices (e.g., Nintendo DS™,PlayStation Portable™, Gameboy Advance™, iPod™), laptops, wearabledevices (e.g. Apple Watch™, Google Glass™), PDAs, portable Internetdevices, music players, data storage devices, or other handheld devices,etc. Various other types of devices would fall into this category ifthey include Wi-Fi or both cellular and Wi-Fi communication capabilitiesand/or other wireless communication capabilities, for example overshort-range radio access technologies (SRATs) such as BLUETOOTH™, etc.In general, the term “UE” or “UE device” may be broadly defined toencompass any electronic, computing, and/or telecommunications device(or combination of devices) which is easily transported by a user andcapable of wireless communication.

Base Station (BS)—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Processing Element—refers to various elements or combinations ofelements that are capable of performing a function in a device, e.g. ina user equipment device or in a cellular network device. Processingelements may include, for example: processors and associated memory,portions or circuits of individual processor cores, entire processorcores, processor arrays, circuits such as an ASIC (Application SpecificIntegrated Circuit), programmable hardware elements such as a fieldprogrammable gate array (FPGA), as well any of various combinations ofthe above.

Wireless Device (or wireless communication device)—any of various typesof computer systems devices which performs wireless communications usingWLAN communications, SRAT communications, Wi-Fi communications and thelike. As used herein, the term “wireless device” may refer to a UEdevice, as defined above, or to a stationary device, such as astationary wireless client or a wireless base station. For example awireless device may be any type of wireless station of an 802.11 system,such as an access point (AP) or a client station (UE), or any type ofwireless station of a cellular communication system communicatingaccording to a cellular radio access technology (e.g. LTE, CDMA, GSM),such as a base station or a cellular telephone, for example.

Wi-Fi—The term “Wi-Fi” has the full breadth of its ordinary meaning, andat least includes a wireless communication network or RAT that isserviced by wireless LAN (WLAN) access points and which providesconnectivity through these access points to the Internet. Most modernWi-Fi networks (or WLAN networks) are based on IEEE 802.11 standards andare marketed under the name “Wi-Fi”. A Wi-Fi (WLAN) network is differentfrom a cellular network.

BLUETOOTH™—The term “BLUETOOTH™” has the full breadth of its ordinarymeaning, and at least includes any of the various implementations of theBluetooth standard, including Bluetooth Low Energy (BTLE) and BluetoothLow Energy for Audio (BTLEA), including future implementations of theBluetooth standard, among others.

Personal Area Network—The term “Personal Area Network” has the fullbreadth of its ordinary meaning, and at least includes any of varioustypes of computer networks used for data transmission among devices suchas computers, phones, tablets and input/output devices. Bluetooth is oneexample of a personal area network. A PAN is an example of a short rangewireless communication technology.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thusthe term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Configured to—Various components may be described as “configured to”perform a task or tasks. In such contexts, “configured to” is a broadrecitation generally meaning “having structure that” performs the taskor tasks during operation. As such, the component can be configured toperform the task even when the component is not currently performingthat task (e.g., a set of electrical conductors may be configured toelectrically connect a module to another module, even when the twomodules are not connected). In some contexts, “configured to” may be abroad recitation of structure generally meaning “having circuitry that”performs the task or tasks during operation. As such, the component canbe configured to perform the task even when the component is notcurrently on. In general, the circuitry that forms the structurecorresponding to “configured to” may include hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112, paragraph six, interpretation for thatcomponent.

FIG. 1—Example First Device Connecting to BT Devices

FIG. 1 shows an example first device 106 which may be owned by and/oroperated by a first user. The first device 106 may selectively connectover a wireless connection such as BLUETOOTH™ (BT) with various devices,such as a tablet computer 114, one or more smart phones 116, a computer118, a remote control 120, a keyboard 122, a headset or speaker 124,and/or remote game controllers (GC) 126 and 128, etc. In the exampleshown in FIG. 1, the first device 106 is shown as being possiblyconnected with a number of BT devices, although the first device 106 mayconnect to any of various types of devices. In this example embodiment,the first device may be any of various types of devices, such as acomputer, tablet, smart phone, wearable device, etc.

The first device 106 is also shown as being connected through a widearea network 108 to a server computer 110. The server computer 110 maystore information regarding other devices associated with or owned bythe first user, e.g., as indicated by a first user account. For example,the server 110 may be a cloud-based server which stores informationregarding other devices owned by the first user. The first device 106may connect to the server 110 through network 108 over a Wi-Fi network,e.g., through a Wi-Fi access point for an Internet connection.Alternatively, or in addition, the first device 106 may connect to theserver 110 through network 108 over a cellular connection. As will befurther discussed below, the first device 106 may operate to create apairing (establish short-range wireless communications) with a wirelessdevice and in the process create and store link information. The linkinformation may include any data, security credentials (e.g. securitykeys), link keys, long term keys, OOB keys, etc. depending on theshort-range wireless communications protocol through which the firstdevice 106 is paired with the wireless device.

The introduction of proximity pairing, as described above, alsointroduces several challenges, including but not limited to host-hostcalibration differences, environmental variations, and impact of Wi-Fiwhen associated with 2.4 GHz networks. There are some host systems thatare more susceptible to these factors than other host systems. Forexample, when there are several hosts in the vicinity, the userinterface (UI) for proximity pairing (PP) should be displayed only onthe host device for which the pairing is intended, and should not bedisplayed on any of the other hosts in the vicinity. To alleviate someof these issues, the proximity pairing/switching may be based onlimiting the pairing to a specified or selected set of devices. Forexample, in some embodiments a cloud-based proximity pairing/switchingbetween devices (e.g. between accessory devices and electrical/userdevices) may help limit the access to a user's cloud-based devices. Thismay provide a seamless experience for the user to help use an accessorydevice with the intended (correct) electronic/user device at theintended time. The first device 106 may then be configured to providethe link information (or other connection information) to the server 110so that this link information may be shared with other devicesassociated with or owned by the first user. These other devices may beconsidered as the specified or selected (set of) devices with which thefirst device 106 may be paired.

FIG. 2—Example First Computer System Connecting to BT Devices

FIG. 2 illustrates an example where the first device 106 may be acomputer system. Thus FIG. 2 shows an example of a first computer system106A connected to one or more of various types of wireless devices. Inthis example embodiment, the first computer system 106A may connect to awireless mouse 130, wireless keyboard 122, wireless trackpad 132, and/orwireless headphones/earbuds/speaker 124. In addition, the first computersystem 106A may establish communications over a wide area network 108,such as the Internet, using any of various communication technologies,such as Wi-Fi, cellular, or a wired connection, and may also communicatevia network 108 communicate with a remote device/server 110 (forexample). Furthermore, computer system 106A may wirelessly connect to astreaming device 138 (e.g. AppleTV™), and may connect with variousmobile devices such as tablets 114 and cellular phones 116. Overall, itshould be noted that the first device 106 (such as computer device 106A)may connect over a WPAN to any one or more of the devices enumeratedabove, and any other similar devices equipped, for example, with shortrange wireless communication interfaces, e.g. BT and the like.

FIG. 3—Example Block Diagram of a Device

FIG. 3 illustrates an exemplary block diagram of a device 106, such asthe first device 106 in FIG. 1 and/or computer device 106A in FIG. 2. Asshown, the device 106 may include processor(s) 302, which may executeprogram instructions for the device 106 and may comprise displaycircuitry 304 which may perform graphics processing and provide displaysignals to the display 340. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, Flashmemory 310) and/or to other circuits or devices, such as the displaycircuitry 304, radio 330, connector I/F 320, and/or display 342. The MMU340 may be configured to perform memory protection and page tabletranslation or set up. In some embodiments, the MMU 340 may be includedas a portion of the processor(s) 302.

As shown, the processor 302 may be coupled to various other circuits ofthe device 106. For example, the device 106 may include various types ofmemory, a connector interface 320 (e.g., for coupling to the computersystem), the display 342, and wireless communication circuitry (e.g.,for Wi-Fi, BLUETOOTH′, LTE, LTE-A, GPS, etc.). The device 106 mayinclude at least one antenna (e.g. 335 a), and possibly multipleantennas (e.g. illustrated by antennas 335 a and 335 b), for performingwireless communication with base stations and/or other devices. Antennas335 a and 335 b are shown by way of example, and UE device 106 mayinclude more antennas. Overall, the one or more antennas arecollectively referred to as antenna 335. For example, the device 106 mayuse antenna 335 to perform the wireless communication with the aid ofradio 330. As noted above, the UE may be configured to communicatewirelessly using multiple wireless communication standards in someembodiments.

As described further subsequently herein, the device 106 may includehardware and software components for implementing improved methods forpairing and connecting with accessory devices. For example, the deviceof a user may store and execute a wireless software driver (e.g., aBLUETOOTH™ protocol stack), or other software, for providing linkinformation associated with an accessory device to a server to be sharedwith other devices associated with the user. The device 106 may beconfigured to implement part or all of the methods described herein,e.g., by executing program instructions stored on a memory medium (e.g.,a non-transitory computer-readable memory medium) and/or throughhardware or firmware operation. In other embodiments, the methodsdescribed herein may be at least partially implemented by a programmablehardware element, such as an FPGA (Field Programmable Gate Array),and/or as an ASIC (Application Specific Integrated Circuit). Thus thedevice 106 may be configured to implement methods according to any ofvarious embodiments disclosed herein.

In some embodiments, radio 330 may include separate controllersdedicated to controlling communications for various respective RATstandards. For example, as shown in FIG. 3, radio 330 may include aWi-Fi controller 356 and a BLUETOOTH™ controller 354, and may alsocomprise a cellular controller (e.g. LTE controller) 352. In someembodiments, one or more or all of these controllers may be implementedas hardware, software, firmware or some combination thereof. While threeseparate controllers are illustrated within radio 330, other embodimentsmay have fewer, more, and/or different controllers for various differentRATs that may be implemented in device 106.

It should also be noted that any of the accessory devices exemplified inFIG. 2 may also include certain components described in FIG. 3 ascomponents of first device 106. For example, a headset accessory device(e.g. 124 in FIG. 2) may include radio circuitry for short rangewireless communications, e.g. a BLUETOOTH™ controller such as controller354 shown in FIG. 3, in addition to various other components particularto the functionality and purpose of the accessory device (e.g. speakers,transducers, etc.).

FIG. 4—Accessory Device Sharing

FIG. 4 shows the flow chart for an example method by which an accessorydevice may transition from a connection with a first device toconnecting to a second device, according to some embodiments. The firstdevice and the second device may be any of various previously enumeratedand/or described devices, such as device 106, and in some scenarios maybelong to different classes of devices. In some embodiments the firstdevice and second device may also be included in a specified group ofdevices or a designated set of devices, for example they may beassociated with a common user account (e.g., a cloud-based account, suchas an iCloud™ account) of a user which may be maintained by acloud-based server. In other embodiments the devices may be groupedand/or designated as belonging to a group of devices based on anothercriteria. In general, the devices may be considered as part of a groupof devices, e.g. a group of trusted devices. The accessory device may beany of various devices as described above in relation to FIG. 1 and FIG.2, such as a headset, game controller, mouse, keyboard, wearable, orother similar device, including at least components that facilitate andenable short range wireless communication for pairing with the firstdevice and the second device.

At 402, the first device may pair with the accessory device. In someembodiments, user input on the first device or the accessory device mayinitiate the pairing or the pairing may occur automatically. Forexample, the first device may exchange a pairing request with theaccessory device for the purpose of establishing a connection betweenthe devices. The accessory device may be able to connect with the firstdevice by one or more of various means, including wired or wirelessconnections. For example, the accessory device may be a BLUETOOTH™ (BT)device, which may operate to connect to the first device wirelessly,using BT technology. In general, the accessory device may operate toconnect to the first device wirelessly, using any of various availableWPAN technologies, or short range wireless communications technologies.

At 404 the first device may communicate information associated with thefirst pairing (or with the first pairing request) to a central locationsuch as a server, e.g. a cloud-based server. The cloud-based server maystore respective information associated with various other devices thatbelong to the specified group of devices into which the first devicealso belongs, for example devices that all belong to the user of thefirst device, or are designated as being used by the user of the firstdevice. For example, if the user owns a portable computer, a tabletdevice and a smart phone, the server (central location) may storerespective information associated each of these three devices. Theserver may also have the ability to communicate, e.g., push, data toeach of these three devices. The information (associated with the firstpairing) communicated by the first device to the cloud-based server maycomprise various items relevant to the accessory device and/or toestablishing a connection with the accessory device, such as link keys,addresses, and/or other information. The information may be communicatedautomatically as a result of the pairing between the first device andthe accessory device, or the communication of the information may betriggered by user input on the first device or a request for theinformation by the cloud-based server. If the first device uses BT toconnect to the accessory device, the BT software stack may operate toconvey the information to the cloud-based server. The first device maycommunicate with the cloud-based server by various means, such as wiredor wireless connections to the Internet, e.g., using Wi-Fi, LTE, wiredInternet, or related technologies. The cloud-based server may store theinformation and/or distribute the received information among one or more(or all other) devices associated with/belonging to the specified (ordesignated) group of devices, e.g. devices associated with the useraccount of the user of the first device. Thus, as shown at 406, theinformation associated with the accessory device (and the first pairingrequest) may be propagated from the first device to other devices in thespecified group, e.g. to other devices associated with the same user,such as the second device. In some embodiments the second device maythen store the information.

The information associated with the pairing (request) of the accessorydevice and the first device may also be referenced as link informationassociated with the pairing, and hence include information pertaining toboth the accessory device and the first device as associated with thefirst pairing. Accordingly, the link information may include a firstportion pertaining to the first device and a second portions pertainingto the accessory device. For example, the first portion of the linkinformation may include security credentials of the first device, andthe second portion of the link information may include securitycredentials of the accessory device. Furthermore, the first device alsomay send the link information associated with one or more other userdevices (also referred to as second link information) to the accessorydevice. By providing this (second) link information to the accessorydevice, the accessory device is enabled to automatically connect(without having to undergo a pairing procedure which may or may notrequire user intervention) with a second user device of the otherspecified user devices, using the first link information previouslystored at the second user device and the second link informationpreviously stored at the accessory device.

As shown in the flow diagram of FIG. 4, the first device connects withthe server (or, more generally, with an external device capable ofreceiving, storing and sharing information, including the linkinformation, about other devices), to establish what information aboutother devices is stored on the server (404). However, it should be notedthat at any point in time the first device may already have previouslyreceived the second link information, and in that case the first deviceneed not be connected to the server as it may already be storing thisinformation. In other words, the first device may already have storedlink information associated with (or corresponding to) the one or moreother user devices, and may use this locally stored history to createthe connection credentials for the one or more other devices.Accordingly, 404 may not need to take place and be omitted in suchscenarios.

At 410, certain conditions and/or actions may trigger an indication forthe second user device to pair with the accessory device. For example,in some embodiments, the second device may determine its proximity tothe accessory device. Proximity between the second device and theaccessory device may be calculated using various metrics, such as signalstrength, and may be compared to a threshold value to determine whetherto initiate proximity-based pairing. In case of proximity-based pairing,if the accessory device is determined to be at least within specifiedproximity of the accessory device, at 412 the second device mayautomatically connect with the accessory device (without requiring apairing procedure) or may present the user with an option to pair thesecond device to the accessory device, e.g., by prompting the user witha pop-up UI inquiring whether to connect to the accessory device, asdesired. The distance used to trigger pairing or connecting can be setas any desired or specified distance. In some implementations, theproximity may be set to a distance determined to be a distance at whichpairing/connecting is expected. User input on the second device, e.g.,through user interaction with buttons and/or a display, may indicate adesire to pair with the accessory device. Alternately, the second userdevice may simply connect with the accessory device using the previouslystored link information (at both the second user device and at theaccessory device as described above) without requiring any userinteraction and/or without requiring any multi-step pairing procedure.

As mentioned above, at 412 the second user device may operate to pairwith the accessory device in response to the indication received at 410.As the accessory device may already be actively paired with the firstdevice, the second device may communicate a disconnect message to thefirst device (e.g., over the Internet or through the cloud-based server)for the purpose of transitioning the accessory device from the firstuser device to the second user device. In some implementations, theaccessory may alternatively communicate the disconnect message. Thesecond user device may use the information received at 404/406, such aslink key information associated with the accessory device, in order toconnect with the accessory device. Similarly, the accessory device mayuse the information received at 408, such as link key informationassociated with the second user device, in order to connect with thesecond user device. This enables the second user device and theaccessory device to more easily and efficiently connect with each otherwithout requiring a pairing procedure. Thus, the accessory device maydisconnect from the first user device and may establish a new connectionwith the second user device.

FIGS. 5 and 6 provide an illustration of how the pairing processdescribed in FIG. 4 may be used to connect user devices to accessorydevices via short range wireless communications according to one set ofembodiments. As shown in FIG. 5, when a user pairs an accessory device508, shown here as a headset, via BLUETOOTH™ (BT) to any one of theuser's registered devices, shown here as a computer 504, e.g. an iMac™,the device, e.g., through the BT stack, may opt to send the linkinformation associated with the pairing (of user device 504 withaccessory device 508) via the cloud 502 to other devices in the user'sregistered account. As an example, a second user device 506 is shown inFIG. 5 as a smart phone. If any of the other user devices, e.g. userdevice 506, intend to use the accessory device 508, then the linkinformation, e.g. link keys, may be relayed to the accessory device 508from the currently connected device 504. Then, as shown in FIG. 6, whenthe accessory device 508 is moved into pairing proximity range of thesecond user device 506, the disconnect message may be sent over thecloud 502 to the currently connected device 504, enabling proximityswitching. Accordingly, accessory device 508 may be connected withsecond user device 506 using the link information associated with seconduser device 506 that had been provided to the accessory device 508 andthe link information associated with accessory device 508 that had beenprovided to second user device 506. Thus, the technique obviates theneed for a more lengthy pairing process, either automatic or manual,that requires an exchange—one or both ways—of link information (e.g.keys).

FIG. 7 shows a communications system with devices connected and pairedaccording to some other embodiments. More specifically, FIG. 7 providesan illustration of the types of wired and wireless connections that maybe established in order to allow user devices and accessory devices tobe easily connected and/or paired with each other, respectively. A userdevice 702 and an accessory device 708 may be connected over a securetransport such as USB 714 (shown) or secure Wi-Fi (more generally asecure wired or wireless connection), and the existing transport may beused for exchanging Bluetooth security credentials (more generally linkinformation corresponding to establishing a pairing between the devicesaccording to an insecure and/or short range wireless communicationprotocol) between devices 702 and 708. In case a BLUETOOTH™ connection(or more generally a connection or pairing according to an insecureand/or short range wireless communication protocol) is desired betweenmore than two devices, device 702 that has a connection with devices 704and 706 may act as a relay to transfer BLUETOOTH™ security credentials(more generally link information corresponding to establishing a pairingbetween the devices according to the insecure and/or short rangewireless communication protocol) over the existing BLUETOOTH™ (or moregenerally the insecure and/or short range wireless communicationprotocol) connections to bring up the third connection between devices704 and 706 without devices 704 and 706 having to go through a pairingprocedure.

Some embodiments of the system shown in FIG. 7 may include a hand helddevice 702 connected to both a first type of accessory device 704 and toa second type of device 706, for example a wearable device 706. Theexisting BLUETOOTH™ (BT) connection(s) 710 and 712 may be used toexchange BT security credentials of the first type of accessory device704 and the wearable device 706 between the first type of accessorydevice 704 and the wearable device 706. Devices 704 and 706 may thenconnect with each other under certain conditions without requiring apairing procedure. In another example, a hand held device 702 may beconnected to a display device 708 (e.g. a CarPlay™ device) over USBusing an iAP™ protocol. The existing USB connection may be used toexchange BT security credentials and automatically connect the hand helddevice 702 and the display device 708. In yet another example, a handheld device may be connected to a second type of accessory device over asecure Wi-Fi connection. The existing Wi-Fi connection may be used toexchange BT security credentials and automatically connect the hand helddevice and second type accessory devices.

Easy Pairing Procedure

Pursuant to the above, the following may be performed to facilitatepairing as described, for example, in FIGS. 4, 5, 6, and 7. First, apairing type may be determined. Based upon the device types andapplication, one of a number of different types of pairings may beselected/identified. A first type of pairing may be pairing using a linkkey. This pairing method may be used for classic pairing between BR/EDR(Basic Rate/Enhanced Data Rate) devices or dual mode devices, where linkkey is generated on one device and sent to other device for easypairing. A second type of pairing may be pairing using long term key.This pairing method may be used for LE (Low Energy) pairing between twodual mode devices or LE devices, where LTK (Long Term Key) and other LEpairing related keys are generated on both devices and then exchangedwith one another. A third type of pairing may be pairing using OOB (Outof Band) data. This pairing method may be used when either of the abovemethods are not possible to select for application specific reason. Whenthis pairing type is selected, OOB keys (e.g. as defined by OOBassociation model in BLUETOOTH™ core spec 2.1 and later) may begenerated and exchanged over OOB transport.

Second, device information discovery may be performed. The OOB transportmay be used to read device specific information for the devices whichare desired to be BT paired. Accordingly, the following data may beretrieved over OOB transport: the BT address of the device, BT devicename of the device, and COD (class of device) of the device (when deviceis BR/EDR or dual mode device). Third, a link key may be generated. Anapplication running on the user device side may provide the remotedevice information and pairing type to the BT stack and may request togenerate security keys for the specific pairing type. Fourth, the linkkeys may be exchanged. The generated security keys may be exchanged overexisting non-BT transport and stored in the respective securitydatabase.

Embodiments of the present invention may be realized in any of variousforms. For example, in some embodiments, the present invention may berealized as a computer-implemented method, a computer-readable memorymedium, or a computer system. In other embodiments, the presentinvention may be realized using one or more custom-designed hardwaredevices such as ASICs. In other embodiments, the present invention maybe realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory medium(e.g., a non-transitory memory element) may be configured so that itstores program instructions and/or data, where the program instructions,if executed by a computer system, cause the computer system to perform amethod, e.g., any of a method embodiments described herein, or, anycombination of the method embodiments described herein, or, any subsetof any of the method embodiments described herein, or, any combinationof such subsets.

In some embodiments, a device (e.g., a UE) may be configured to includea processor (or a set of processors) and a memory medium (or memoryelement), where the memory medium stores program instructions, where theprocessor is configured to read and execute the program instructionsfrom the memory medium, where the program instructions are executable toimplement any of the various method embodiments described herein (or,any combination of the method embodiments described herein, or, anysubset of any of the method embodiments described herein, or, anycombination of such subsets). The device may be realized in any ofvarious forms.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

The invention claimed is:
 1. A wireless accessory device comprising: aprocessor configured to cause the wireless accessory device to performoperations comprising: communicating directly via a direct wirelesscommunication link with a host device; and receiving, from the hostdevice via the direct wireless communication link, a first item of linkinformation stored in the host device and associated with a first devicedifferent from the host device, wherein the first item of linkinformation permits the accessory device to subsequently establish adirect wireless link with the first device without first engaging in apairing procedure with the first device.
 2. The wireless accessorydevice of claim 1, wherein a set of devices associated with a commonuser comprises the host device and the first device.
 3. The wirelessaccessory device of claim 1, wherein the first item of link informationcomprises: a link key; a long term key; a security credential; anaddress; or an out of band key.
 4. The wireless accessory device ofclaim 1, wherein the operations further comprise: automaticallyestablishing the direct wireless link when the accessory device comeswithin a predetermined range of the first device.
 5. The wirelessaccessory device of claim 1, wherein the direct wireless link comprisesa Bluetooth connection.
 6. The wireless accessory device of claim 5,wherein the first item of link information comprises at least one of: aBluetooth address; a Bluetooth device name; or a class of device.
 7. Thewireless accessory device of claim 1, wherein the operations furthercomprise: receiving, via the direct wireless link from the first device,a second item of link information associated with a second devicedifferent from the first device, wherein the second item of linkinformation permits the accessory device to establish a direct secondwireless link with the second device without first engaging in a pairingprocedure with the second device.
 8. A method comprising: establishing awireless communication link directly between an accessory device and afirst device, wherein the wireless communication link is establishedwithout the accessory device and the first device engaging in a pairingprocedure, and wherein the wireless communication link is establishedusing an item of link information associated with the first device,wherein the item of link information was stored in a host devicedifferent from the first device and provided directly to the accessorydevice by the host device via a second wireless communication linkestablished between the accessory device and the host device.
 9. Themethod of claim 8, wherein a set of devices associated with a commonuser comprises the host device and the first device.
 10. The method ofclaim 8, wherein the first item of link information comprises: a linkkey; a long term key; a security credential; an address; or an out ofband key.
 11. The method of claim 8, further comprising: establishingthe wireless communication link in response to the accessory devicecoming within a predetermined range of the first device.
 12. The methodof claim 8, wherein the wireless communication link comprises aBluetooth connection.
 13. The method of claim 12, wherein the first itemof link information comprises: a Bluetooth address; a Bluetooth devicename; or a class of device.
 14. The method of claim 8, furthercomprising: providing, via the wireless communication link from thefirst device to the accessory device, a second item of link informationassociated with a second device different from the first device;terminating the wireless communication link; and establishing, using thesecond item of link information and subsequent to terminating thewireless communication link, a new direct wireless link between theaccessory device and the second device without the accessory devicefirst engaging in a pairing procedure with the second device.
 15. Anon-transitory memory element storing instructions executable by aprocessor to cause a wireless accessory device to: communicate directlyvia a direct wireless communication link with a host device; andreceive, via the wireless communication link from the host device, afirst item of link information stored in the host device and associatedwith a first device different from the host device, wherein the firstitem of link information permits the accessory device to subsequentlyestablish a direct wireless link with the first device without firstengaging in a pairing procedure with the first device.
 16. Thenon-transitory memory element of claim 15, wherein a set of devicesassociated with a common user comprise the host device and the firstdevice.
 17. The non-transitory memory element of claim 15, wherein thefirst item of link information comprises: a link key; a long term key; asecurity credential; an address; or an out of band key.
 18. Thenon-transitory memory element of claim 15, wherein the instructions areexecutable by the processor to cause the wireless accessory device toautomatically establish the direct wireless link when the accessorydevice comes within a predetermined range of the first device.
 19. Thenon-transitory memory element of claim 15, wherein the direct wirelesslink comprises a Bluetooth connection; and wherein the first item oflink information comprises: a Bluetooth address; a Bluetooth devicename; or a class of device.
 20. The non-transitory memory element ofclaim 15, wherein the instructions are executable by the processor tocause the wireless accessory device to: receive, via the direct wirelesslink from the first device, a second item of link information associatedwith a second device different from the first device, wherein the seconditem of link information permits the accessory device to establish asecond direct wireless link with the second device without firstengaging in a pairing procedure with the second device.